Repository navigation
feat(release): publish CLI archives to the fork's GitHub Release and update from it - #2
Merged
Merged
Conversation
…update from it Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> The release job was gated to the upstream owner, so the fork never produced CLI archives, and `multica update` plus the install scripts read upstream releases only. - release.yml: run GoReleaser on the fork (Homebrew skipped), keep desktop upstream-only - goreleaser: bake the building repository into the CLI as the update source - update.go: MULTICA_RELEASE_REPO overrides the release repository at runtime - install.sh/install.ps1: MULTICA_RELEASE_REPO selects the release repository; Homebrew is skipped when set
…itory's releases Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Add a single RELEASE_REPO constant and use it for the latest-release fetch, the all-releases link and the install command (which now sets MULTICA_RELEASE_REPO).
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
The
releasejob was gated to the upstream owner, so this fork never produced CLI archives, andmultica updateplus the install scripts only read upstream releases. Users therefore could not receive daemon-side fixes such as the Graph cancel stop-evidence fix shipped server-side in v0.1.2.release.yml: run GoReleaser on this repository too, skipping Homebrew (the tap is upstream-only). Thedesktopjob stays upstream-only..goreleaser.yml: bake the building repository into the CLI (cli.DefaultReleaseRepo) somultica updatereads releases from where the binary was built.update.go:MULTICA_RELEASE_REPOoverrides the release repository at runtime.install.sh/install.ps1:MULTICA_RELEASE_REPOselects the download repository; Homebrew is skipped when it is set.Verification
go test ./internal/cli -run 'ReleaseAPIURL|Update'passes.bash -n scripts/install.shpasses.Not verified
install.ps1was not executed./downloadpage and landing install command still point upstream (not changed here).MULTICA_RELEASE_REPOis set.Test plan
checksums.txton this repository's ReleaseMULTICA_RELEASE_REPO=Time-Machine-Lab/Stein-AI multica updatefinds that releasedesktopand Homebrew steps are skipped on this repository🤖 Generated with Claude Code